The Cassandra Server must generate audit records when privileges/permissions are added.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
|---|---|---|---|---|
| V-72697 | VROM-CS-000285 | SV-87329r1_rule | Medium |
| Description |
|---|
| Changes in the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized elevation or restriction of individuals' and groups' privileges could go undetected. Elevated privileges give users access to information and functionality that they should not have; restricted privileges wrongly deny access to authorized users. In an SQL environment, adding permissions is typically done via the GRANT command, or, in the negative, the DENY command. |
| STIG | Date |
|---|---|
| vRealize - Cassandra Security Technical Implementation Guide | 2017-06-06 |
Details
| Check Text ( C-72853r1_chk ) |
|---|
| Review the Cassandra Server configuration to ensure audit records are generated when privileges/permissions are added. At the command prompt, execute the following command: # grep ' If level is not set to "ALL", this is a finding. |
| Fix Text (F-79101r1_fix) |
|---|
| Configure the Cassandra Server to generate audit records when privileges/permissions are added. At the command line execute the following command: # sed -i 's/^\(\s*\) |